System and Method of Determining Call Treatment of Repeat Calls

ABSTRACT

A method is disclosed that includes retrieving first data associated with a call from an action-object table. The method further includes retrieving second data from a resolution table based on the first data. The second data indicates a treatment type to be provided to the call. The method further includes, in response to determining that the treatment type indicates a particular treatment type, servicing the call with the particular treatment type. The particular treatment type includes routing the call to a destination associated with a call center.

CLAIM OF PRIORITY

The present application claims priority from and is a continuation of U.S. patent application Ser. No. 12/616,248, filed on Nov. 11, 2009 and entitled “SYSTEM AND METHOD OF DETERMINING CALL TREATMENT OF REPEAT CALLS,” which claims priority from and is a continuation of U.S. patent application Ser. No. 11/129,051, issued as U.S. Pat. No. 7,636,432, filed on May 13, 2005 and entitled “SYSTEM AND METHOD OF DETERMINING CALL TREATMENT OF REPEAT CALLS,” the contents of which are expressly incorporated herein by reference in their entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to call treatment and processing of repeat calls by an automated call processing system.

BACKGROUND

The advent of speech-enabled interactive voice response systems has enabled call center organizations to efficiently deploy automated customer service functions in place of live agents, thereby reducing operational costs. However, this cost savings often comes at the price of reduced efficiency, as a live agent often is more effective at addressing particular types of customer inquiries. The use of an interactive voice response system also may lead to frustration on the part of a repeat caller, i.e., a caller who has called a call center at least twice within a certain time period. The repeat caller may be calling to readdress an issue that was unresolved by a previous call. In such instances, the repeat caller may become agitated when the caller is required to navigate the interactive voice response system for a second time rather than addressing the caller's issue directly with a live agent. Alternatively, the repeat caller may be calling again to obtain information and may not expect to receive the assistance of a live agent. For example, the repeat call could be to obtain a bill payment amount that the caller obtained previously but has since misplaced. In such instances, the use of a live agent to assist the repeat caller typically is an inefficient utilization of the live agent as the caller likely would have obtained the same information at a lower cost using an interactive voice response system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a general diagram of a communication system;

FIG. 2 is a general block diagram that illustrates call processing;

FIG. 3 is a general diagram that illustrates an automated call processing system within the communication system of FIG. 1;

FIGS. 4 and 5 are flow charts that illustrate methods of handling calls at the automated call processing system of FIG. 3.

DETAILED DESCRIPTION OF THE DRAWINGS

A call received at a call center is determined to be a repeat call. The repeat call is evaluated to determine whether the repeat call is to receive a first treatment type. The repeat call is serviced with the first treatment type when the repeat call is determined to receive the first treatment type. The repeat call is serviced with a second treatment type when the repeat call is determined to not receive the first treatment type. The second treatment type includes providing access to a self-service automated system.

In a particular embodiment, a computer implemented method includes determining that a call received at a call center is a repeat call. The computer implemented method includes determining whether the repeat call is to receive a first treatment type. The computer implemented method also includes servicing the repeat call with the first treatment type when the repeat call is determined to receive the first treatment type. The computer implemented method further includes servicing the repeat call with a second treatment type when the repeat call is determined to not receive the first treatment type. The second treatment type includes providing access to a self-service automated system.

In another particular embodiment, a system includes a processor and a memory accessible to the processor. The memory includes operational instructions that, when executed by the processor, cause the processor to determine whether a call received at the call center is a repeat call. The memory includes operational instructions that, when executed by the processor, cause the processor to determine whether the repeat call is to receive a first treatment type. The memory also includes operational instructions that, when executed by the processor, cause the processor to service the repeat call with the first treatment type when the repeat call is determined to receive the first treatment type. The memory further includes operational instructions that, when executed by the processor, cause the processor to service the repeat call with a second treatment type when the repeat call is determined to not receive the first treatment type. The second treatment type includes providing access to a self-service automated system.

In another particular embodiment, a computer-readable storage medium comprising operational instructions that, when executed by a processor, cause the processor to determine that a call received at a call center is a repeat call based on a threshold time period. The operational instructions are further executable by the processor to determine whether the repeat call is to receive a first treatment type. The operational instructions are further executable by the processor to service the repeat call with the first treatment type when the repeat call is determined to receive the first treatment type. The operational instructions are further executable by the processor to service the repeat call with a second treatment type when the repeat call is determined to not receive the first treatment type, wherein the second treatment type includes providing access to a self-service automated system.

Referring to FIG. 1, an illustrated embodiment of a communications system 100 that includes a call routing support system is shown. The communications system 100 includes a speech-enabled call routing system (SECRS) 118, such as an interactive voice response system having a speech recognition module. The communications system 100 also includes a plurality of potential call destinations. Illustrative call destinations shown include service departments, such as a billing department 120, a balance information department 122, a technical support department 124, an employee directory department 126, and new service department 128. In practice, a communications network 116 may receive calls from a variety of callers, such as the illustrated callers 110, 112, and 114. In a particular embodiment, the communications network 116 may be a public telephone network, a wireless telephone network, a voice over Internet protocol (VoIP)-type network, or other network capable of supporting communications. As depicted, the SECRS 118 may include a processor 142, a memory 143, a synonym table 144, and an action-object routing module 140. Depending upon implementation, the SECRS 118 may be coupled to and may route calls to various destinations across a local area network (LAN), a wide area network (WAN), an Intranet, an extranet, the public Internet, and/or other communications link or networks, as shown.

Additionally, the SECRS 118 may route calls to an agent, such as the illustrated live operator 130. An illustrative embodiment of the SECRS 118 may be a call center having a plurality of agent terminals attached. Thus, while only a single operator 130 is shown in FIG. 1, it should be understood that a plurality of different agent terminals or types of terminals may be coupled to the SECRS 118, such that a variety of agents may service incoming calls. Moreover, the SECRS 118 may be operable as an automated call routing system.

Referring to FIG. 2, an illustrative block diagram of the action-object routing module 140 as implemented by the processor 142 is depicted. As shown, the action-object routing module 140 may include an acoustic processing model 210, a semantic processing model 220, and an action-object routing table 230. The acoustic model 210 receives speech input 202 (provided by a caller) and provides a corresponding text output 204. The semantic model 220 receives text output 204 directly or indirectly from the acoustic model 210 and produces an action-object table 206 containing salient terms of the speech input 202. In a particular embodiment, the one or more actions and objects in the action-object table 206 may be ordered or ranked according to a confidence level. The confidence level may be used to indicate how likely a given action or object reflects a correct and useable customer instruction.

The action-object routing module 140 employs the action-object routing table 230 to identify a call routing destination 208 based on matching between the action-object pairs of the action-object table 206 to corresponding call routing destination entries of the routing table 230. In a particular embodiment, the action-object routing table 230 may be implemented as a lookup table or a spreadsheet, such as a Microsoft Excel™ spreadsheet. A call received at a call routing network may be routed to the appropriate destination as identified by the call routing destination 208, such as the billing department 120 or the technical support service department 124 depicted in FIG. 1.

Referring to FIG. 3, a particular embodiment of the automated call processing system 300 is illustrated. As shown, the system 300 may include call processing logic 302, a repeat caller definition table 304, a repeat caller action-object table 306 and a special treatment resolution table 308. The repeat caller action-object table 306 includes a plurality of action-object pairs 320. Similarly, the special treatment resolution table 308 includes a plurality of action-object pairs 330.

In a particular embodiment, the repeat caller definition table 304, the repeat caller action-object table 306, and the special treatment resolution table 308 are each implemented as data stored within a computer readable memory. In a particular embodiment, a single computer readable memory may store all of these tables, but in another embodiment separate memory devices may be used to store each of the illustrated tables. Examples of computer readable memory include, but are not limited to, random access memory (RAM), flash memory, cache, hard disk storage, and the like. Further, in one embodiment, the call processing logic 302 is implemented as a software program for use by a computer processing device.

During operation, the automated call processing system 300 activates program logic within the call processing logic unit 302. The call processing logic 302 accesses data from the repeat call definition table 304 to identify a repeat call request. The call processing logic 302 also accesses the action-object table 306 and the special treatment resolution table 308 to determine whether the identified repeat call is to be serviced using a first treatment type (e.g., special treatment) rather than a second treatment type (e.g., standard treatment). Special treatment of a call may include, for example, routing the call to a live agent, whereas the standard treatment may include, for example, forward the call to an automated self-service system. As noted herein, in one embodiment, repeat calls having certain attributes are serviced using the first treatment type, whereas other calls typically are serviced using the second treatment type.

The repeat caller action-object table 306 is accessed by the call processing logic 302 to retrieve specific action-object pairs 320 associated with a call. The specific action-object pairs 320 retrieved from the action-object table 306 may be used as an index to one or more action-object pairs 330 within the special treatment resolution table 308. In a particular embodiment, a first action-object pair 320 corresponds to the repeat call that was received at the automated call processing system 300. A second action-object pair 320 within the action-object pair table 306 corresponds to an action-object pair for a previously received call. A third action-object pair 320 within the action-object table 306 corresponds to a related action-object pair corresponding to the prior call. The call processing logic 302, upon receipt of the action-object pairs 320 from the repeat caller action-object pair table 306 and the special treatment information from special treatment resolution table 308, compares the action-object pair retrieved from the action-object table 306 corresponding to a repeat call to the second action-object pair that corresponds to the prior call. The prior call and the repeat call are identified as being originated by a common caller. In addition, the call processing logic module 302 determines whether the repeat call is identified as associated with an unresolved issue of the caller that would warrant servicing the call with a first treatment type (e.g., special treatment) based on the indexed action-object pair 330 obtained from the special treatment resolution table 308, where the action-object pair 330 indicates whether the corresponding action-object pair 320 of the repeat call is to receive a particular treatment type, such as, for example, special treatment or standard treatment. The call processing system then routes the repeat call to the appropriate destination based on the indicated treatment.

Referring to FIG. 4, a particular embodiment of a method of handling a call received at a call center, such as a call received at the automated call processing system 300, is shown. The method includes receiving a call at the call center at 402. The method further includes determining that the call is a repeat call at 404 and determining whether the repeat call is to receive a first treatment type (e.g., special treatment) at 406. An example of the first treatment type as special treatment includes routing a caller to a live agent instead of to a self-service software system. In a particular embodiment, the determination of whether the call is to receive the first treatment type is based on an action-object pair associated with the repeat call. The action-object pair characterizes the caller request and may be used to determine whether a particular call is a repeat call and/or whether the repeat call is to receive the first treatment type treatment. An example of action-object pairs in an action-object pair table that may be used to determine whether a call is a repeat call or to determine whether a call is to receive the first treatment type is shown below in tables 1 and 2.

TABLE 1 Example of a portion of “Time Periods Defining Repeat Caller” CA Repeat NV Repeat OK Repeat TX Repeat Caller Caller Caller Caller within # of within # of within # of within # of Segment Days Days Days Days Complex 45 45 45 45 Growth 30 30 30 30 Value 7 7 7 7 Basic 7 7 7 7 Other 0 0 0 0

TABLE 2 Example of a portion of “Repeat Caller Action-Objects” Repeat Related Action Objects Logic Related AO 1 AO 2 Acquire-Basic Y Acquire-Basic_DFLT Null Acquire-Basic_DFLT Y Acquire-Basic Null Acquire-Cingular Y |Vague-CingularGroup_DFLT| Inquire-Cingular Acquire-Dish Y Null Null Acquire-DSL Y Null Null Acquire-LD Y Null Null Acquire-NamedServiceAgent Y Null Null Acquire-NamedServiceSystem Y Null Null Acquire-Service_DFLT N Null Null Acquire-Service_ServiceName_DFLT Y Null Null Acquire-Winback Y Null Null AskAction-Complaint_DFLT Y Null Null AskAction-Service_DFLT Y Null Null Cancel-Basic Y Null Null Cancel-Dish N Null Null

The method further includes servicing the repeat call with, for example, a special treatment when the repeat call is determined to receive the first treatment type, at 408. For example, where a repeat call is associated with receipt of special treatment, that repeat call is routed to a live agent to address a caller's problem using a human agent. In this manner, repeat callers that are identified to receive special treatment are provided increased resources, such as the live agent, to assist the caller with an unresolved problem. The method further includes providing, for example, standard treatment to the call instead of special treatment when the call is determined to not require the first treatment type, or to require a second treatment type, at 410.

Referring to FIG. 5, a particular embodiment of a method of handling a call received at an automated call routing system is shown. The method includes receiving a call at the automated call routing system at 502 and determining a threshold time period to determine whether the call qualifies as a repeat call at 504. The method further includes accessing an action-object table to assign a task to the call at 506 and comparing the task of the call to the task of a prior call to determine whether the call is a repeat call at 508.

In a particular embodiment, the method includes comparing an action-object pair of the call to an action-object pair that is related to a prior call to determine whether the call is a repeat call. In a particular illustrative embodiment, the threshold time period is a specified number of days.

Also, in a particular embodiment, the task provided by the caller is determined in connection with a purpose of a call inquiry received at the automated call routing system. The task may be defined by a particular action-object pair assigned to the call. When the call is determined to be a repeat call, the method may determine whether the repeat call is to be serviced with a first treatment type or a second treatment type based on the determined task of the call. An example of the second treatment type includes standard treatment, such as routing the call to a self-service system. An example of the first treatment type includes special treatment, such as routing the call to a live agent terminal at a call handling center.

With the disclosed system and method, a call center organization may use and identify tasks of a particular call to determine whether to resolve a caller's request using self-service automation, which is less expensive, or to route the call to a live agent for greater attention and a personal touch. The disclosed task-dependent repeat call handling system and method is an improvement over the conventional approach in which repeat callers are handled the same way and either all callers are routed to a live agent or to a common self-service system. The disclosed system and method thereby provides enhanced service to select repeat callers having unresolved issues that need immediate attention. Such callers are connected with a call center agent to receive special treatment.

In a particular illustrative embodiment, the method of determining a repeat caller and determining a call treatment may include performing a look-up in a repeat caller definition table for a particular number of days where the call is determined to be a repeat call. If the call is received within the time period then a repeat call flag may be set to ‘yes’. The caller provides a task via a purpose of call field within an enterprise automated call routing system and an action-object pair is assigned to that call based on the task. A table look-up is then made in the repeat caller action-object table to determine if the caller's current action-object matches the action-object from their previous call. If the action-object pairs match then repeat call logic may be identified as active. Also, the action-object pair for the detected call may be compared to a special treatment resolution table to determine how to resolve a particular action-object. For example, where the previous action-object is equal to the detected action-object or where the previous action-object is related to the current action-object, then the caller may be detected as a repeat caller and the caller's task may be subsequently determined to be an unresolved issue. If a repeat caller is identified as having an unresolved issue then the call is routed to a live agent for special treatment as determined by the special treatment resolution table. However, where the call is not a repeat call or where the repeat call is not identified with an unresolved issue, then the call is not provided the special treatment and is routed in the standard manner.

While the disclosed system is described with respect to action-object technology, it should be understood that the system and method disclosed is suitable with alternative call center systems. In addition, the disclosed system and method provides an improved technique to handle repeat callers by allocating live agent resources for those callers likely to have unresolved issues, while efficiently and cost effectively applying self-service system technology for those callers likely to have less urgent needs. Thus, the disclosed system and method may reduce the number of repeat callers handled by a live agent and save significant costs on a per call basis. Such cost considerations are increasingly important as call centers handle larger and larger call volumes.

The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments which fall within the true scope of the present disclosure. Thus, to the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description. 

1. A method comprising: retrieving first data associated with a call from an action-object table; retrieving second data from a resolution table based on the first data, wherein the second data indicates a treatment type to be provided to the call; and in response to determining that the treatment type indicates a particular treatment type, servicing the call with the particular treatment type, wherein the particular treatment type includes routing the call to a destination associated with a call center.
 2. The method of claim 1, wherein the destination includes a billing department, a balance information department, a technical support department, an employee directory department, or a new service department.
 3. The method of claim 1, further comprising, in response to determining that the treatment type does not indicate the particular treatment type, servicing the call with a second particular treatment type, wherein the second particular treatment type includes providing access to a self-service automated system.
 4. The method of claim 3, wherein the particular treatment type is distinct from the second particular treatment type.
 5. The method of claim 1, wherein the particular treatment type includes providing access to a live agent associated with the destination.
 6. The method of claim 1, wherein the resolution table includes a plurality of action-object pair entries, each of the action-object pair entries indicating one of a plurality of treatment types, and wherein none of the plurality of treatment types includes providing access to a self-service automated system.
 7. The method of claim 1, wherein the treatment type indicates the particular treatment type when the call is associated with an unresolved issue of a caller.
 8. The method of claim 1, further comprising determining that the call is a repeat call based on the first data.
 9. The method of claim 1, further comprising determining whether the call is a repeat call based on a comparison of a first action-object pair of the first data to a second action-object pair of the second data, wherein the first action-object pair is associated with the call and the second action-object pair is associated with a prior call.
 10. The method of claim 9, further comprising assigning a task to the call based on determining that the call is a repeat call, wherein the task indicates that the call is associated with an unresolved issue of a caller associated with the call.
 11. The method of claim 9, wherein the second data is accessed from the resolution table based on the first data in response to determining that the call is a repeat call.
 12. A system comprising: a processor; and a memory accessible to the processor, the memory including instructions that, when executed by the processor, cause the processor to perform a method comprising: retrieving first data associated with a call from an action-object table; retrieving second data from a resolution table based on the first data, wherein the second data indicates a treatment type to be provided to the call; and in response to determining that the treatment type indicates a particular treatment type, servicing the call with the particular treatment type, wherein the particular treatment type includes routing the call to a destination associated with a call center.
 13. The system of claim 12, wherein the method further comprises, in response to determining that the treatment type does not indicate the particular treatment type, servicing the call with a second particular treatment type, and wherein the second particular treatment type includes providing access to a self-service automated system.
 14. The system of claim 12, wherein, when the treatment type indicates the particular treatment type, the call is associated with an unresolved issue of a caller associated with the call.
 15. The system of claim 12, wherein the method further comprises: assigning a particular task to the call based on the first data; and comparing the particular task to a task of a prior call to determine whether the call is a repeat call.
 16. The system of claim 12, wherein the second data is retrieved from the resolution table based on the first data in response to determining that the call is a repeat call.
 17. The system of claim 12, wherein the action-object table includes a plurality of action-object pairs, wherein the first data includes an action-object pair, wherein the second data is retrieved from the resolution table using an index, and wherein the action-object pair is the index.
 18. The system of claim 12, wherein the method further comprises receiving task-identification information from a caller that initiated the call.
 19. A computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to perform a method comprising: retrieving first data associated with a call from an action-object table; retrieving second data from a resolution table based on the first data, wherein the second data indicates a treatment type to be provided to the call; and in response to determining that the treatment type indicates a particular treatment type, servicing the call with the particular treatment type, wherein the particular treatment type includes routing the call to a destination associated with a call center.
 20. The computer-readable storage medium of claim 19, wherein the method further comprises, in response to determining that the treatment type does not indicate the particular treatment type, servicing the call with a second particular treatment type, and wherein the second particular treatment type includes providing access to a self-service automated system. 